System and method for providing network address information in a server system

ABSTRACT

A cPCI server system includes a plurality of host processor cards. A management card is coupled to the plurality of host processor cards via at least one bus. The management card includes at least one user interface for receiving network address information from a user. The management card is configured to send received network address information to the plurality of host processor cards via the at least one bus, thereby configuring the host processor cards for management LAN communications.

THE FIELD OF THE INVENTION

[0001] The present invention relates to server systems. Moreparticularly, the invention relates to a system and method for providingnetwork address information in a cPCI server system for configuration ofhost processor cards.

BACKGROUND OF THE INVENTION

[0002] Console communications are used in server systems to send andreceive status, control and configuration information. If consolecommunications are sent over a LAN using the TCP/IP protocol, the hostprocessor cards on the LAN must be configured and provided Internetprotocol (IP) address information. Console LAN communications cannot beestablished without having the correct IP settings. Most solutions inthe marketplace use a serial, RS232 interface as the path to set up theIP address information. This requires a separate port connection toevery host processor card. Using an RS-232 port works okay for astandalone server, but when the server is integrated with many others ina common chassis, a separate cable for each server is difficult tomaintain and configure. Alternatively, dynamic host configurationprotocol (DHCP) could be used to get a random address, but this requiresthat the proper subnet mask be preset. Furthermore, random IP addressesare not appropriate for servers because clients need to know their exactaddress.

[0003] It would be desirable to use a single interface in a serversystem to provide IP address information to all host processor cards inthe server system.

SUMMARY OF THE INVENTION

[0004] One form of the present invention provides a server systemincluding a plurality of host processor cards. A management card iscoupled to the plurality of host processor cards via at least one bus.The management card includes at least one user interface for receivingnetwork address information from a user. The management card isconfigured to send received network address information to the pluralityof host processor cards via the at least one bus, thereby configuringthe host processor cards for management LAN communications.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005]FIG. 1 is a front perspective view illustrating a server systemaccording to one embodiment of the present invention.

[0006]FIG. 2 is a rear perspective view illustrating the server systemshown in FIG. 1.

[0007]FIG. 3 is a block diagram illustrating major components of aserver system according to one embodiment of the present invention.

[0008]FIG. 4 is a front view of one of LCD panels used by a serversystem according to one embodiment of the present invention.

[0009]FIG. 5 is an electrical block diagram illustrating majorcomponents of a server management card (SMC) according to one embodimentof the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] In the following detailed description of the preferredembodiments, reference is made to the accompanying drawings that form apart hereof, and in which is shown by way of illustration specificembodiments in which the invention may be practiced. It is to beunderstood that other embodiments may be utilized and structural orlogical changes may be made without departing from the scope of thepresent invention. The following detailed description, therefore, is notto be taken in a limiting sense, and the scope of the present inventionis defined by the appended claims.

[0011] I. Server System

[0012]FIG. 1 is a front perspective view illustrating a server system100 according to one embodiment of the present invention. FIG. 2 is arear perspective view illustrating server system 100. Server system 100includes panels 102, liquid crystal display (LCD) panels 104A and 104B(collectively referred to as LCD panels 104), backplane 106, chassis108, and dual redundant power supply units 114A and 114B (collectivelyreferred to as power supply units 114). Panels 102 are attached tochassis 108, and provide protection for the internal components ofserver system 100. Backplane 106 is positioned near the center of serversystem 100. Backplane 106 is also referred to as midplane 106. LCDpanels 104A and 104B are substantially identical, except for theirplacement on server system 100. LCD panel 104A is positioned on a frontside of server system 100, and LCD panel 104B is positioned on a backside of server system 100.

[0013] Power supply units 114 are positioned at the bottom of serversystem 100 and extend from a back side of server system 100 to a frontside of server system 100. Power supply units 114 each include anassociated cooling fan 304 (shown in block form in FIG. 3). In one formof the invention, additional cooling fans 304 are positioned behind LCDpanel 104B. In one embodiment, 4 chassis cooling fans 304 are used inserver system 100. In an alternative embodiment, 6 chassis cooling fans304 are used. Other numbers and placement of cooling fans 304 may beused. In one form of the invention, cooling fans 304 form an N+1redundant cooling system, where “N” represents the total number ofnecessary fans 304, and “1” represents the number of redundant fans 304.

[0014] In one embodiment, server system 100 supports the CompactPeripheral Component Interconnect (cPCI) form factor of printed circuitassemblies (PCAs). Server system 100 includes a plurality of cPCI slots110 for receiving cards/modules 300 (shown in block form in FIG. 3). Inone embodiment, system 100 includes ten slots 110 on each side ofbackplane 106 (referred to as the 10 slot configuration). In analternative embodiment, system 100 includes nineteen slots 110 on eachside of backplane 106 (referred to as the 19 slot configuration).Additional alternative embodiments use other slot configurations.

[0015]FIG. 3 is a block diagram illustrating major components of serversystem 100. Server system 100 includes backplane 106, a plurality ofcards/modules 300A-300G (collectively referred to as cards 300), fans304, electrically erasable programmable read only memory (EEPROM) 314,LEDs 322, LCD panels 104, power supply units (PSUs) 114, and temperaturesensor 324. Cards 300 are inserted in slots 110 (shown in FIGS. 1 and 2)in system 100. In one form of the invention, cards 300 may occupy morethan one slot 110. In one embodiment, cards 300 include host processorcards 300A, hard disk cards 300B, managed Ethernet switch cards 300C and300D, a server management card (SMC) 300E, and 2 redundant SMC localarea network (LAN) rear transition modules (RTMs) 300F and 300G. In oneembodiment, there is one managed Ethernet switch card 300C fitted in the10 slot chassis embodiment, and up to two managed Ethernet switch cards300C and 300D fitted in the 19 slot chassis embodiment. In one form ofthe invention, managed Ethernet switch cards 300C and 300D are“Procurve” managed Ethernet switch cards.

[0016] In one embodiment, two types of host processor cards 300A may beused in server system 100—PA-RISC host processor cards and IA32 hostprocessor cards. Multiple host processor cards 300A and hard disk cards300B are used in embodiments of server system 100, but are eachrepresented by a single card in FIG. 3 to simply the figure. In one formof the invention, up to 8 host processor cards 300A are used in the 10slot configuration, and up to 16 host processor cards 300A are used inthe 19 slot configuration In one embodiment, each of cards 300 can behot swapped.

[0017] In one embodiment, cards 300 each include a pair of EEPROMs 302Aand 302B, which are discussed below. Power supply units 114 each includean EEPROM 323 for storing power supply identification and statusinformation. Fans 304 include associated sensors 306 for monitoring thespeed of the fans 304. In one embodiment, LEDs 322 include eight statusLEDs, six LAN LEDs to indicate the speed and link status of LAN links318, a blue hot swap status LED to indicate the ability to hot swap SMC300E, a power-on indicator LED, and three fan control indicator LEDs.

[0018] The operational health of cards 300 and system 100 are monitoredby SMC 300E to ensure the reliable operation of the system 100. SMC 300Eincludes serial ports 310 (discussed below), and an extraction lever 308with an associated switch. In one embodiment, all cards 300 include anextraction lever 308 with an associated switch.

[0019] In one embodiment, SMC 300E is the size of a typical compact PCI(cPCI) card, and supports PA-RISC and the IA32 host processor cards300A. SMC 300E electrically connects to other components in system 100,including cards 300, temperature sensor 324, power supply units 114,fans 304, EEPROM 314, LCD panels 104, LEDs 322, and SMC rear transitionmodules 300F and 300G via backplane 106. In most cases, the connectionsare via I²C buses 554 (shown in FIG. 5), as described in further detailbelow. The I²C buses 554 allow bi-directional communication so thatstatus information can be sent to SMC 300E and configuration informationsent from SMC 300E. In one embodiment, SMC 300E uses I²C buses 554 toobtain environmental information from power supply units 114, hostprocessor cards 300A, and other cards 300 fitted into system 100.

[0020] SMC 300E also includes a LAN switch 532 (shown in FIG. 5) toconnect console management LAN signals from the host processor cards300A to an external management network (also referred to as managementLAN) 320 via one of the two SMC rear transition modules 300F and 300G.In one embodiment, the two SMC rear transition modules 300F and 300Geach provide external 10/100Base-T LAN links 318 for connectivity tomanagement LAN 320. In one embodiment, SMC rear transition modules 300Fand 300G are fibre-channel, port-bypass cards

[0021] Managed Ethernet switch cards 300C and 300D are connected to hostprocessor cards 300A through backplane 106, and include external10/100/1000Base-T LAN links 301 for connecting host processor cards toexternal customer or payload LANs 303. managed Ethernet switch cards300C and 300D are fully managed LAN switches.

[0022] II. LCD Panel

[0023]FIG. 4 is a front view of one of LCD panels 104. In one form ofthe invention, each LCD panel 104 includes a 2×20 LCD display 400, 10alphanumeric keys 402, 5 menu navigation/activation keys 404A-404E(collectively referred to as navigation keys 404), and a lockout key 406with associated LED (not shown) that lights lockout key 406. If a userpresses a key 402, 404, or 406, an alert signal is generated and SMC300E polls the LCD panels 104A and 104B to determine which LCD panel wasused, and the key that was pressed.

[0024] Alphanumeric keys 402 allow a user to enter alphanumeric stringsthat are sent to SMC 300E. Navigation keys 404 allow a user to navigatethrough menus displayed on LCD display 400, and select desired menuitems. Navigation keys 404A and 404B are used to move left and right,respectively, within the alphanumeric strings. Navigation key 404C is an“OK/Enter” key. Navigation key 404D is used to move down. Navigation key404E is a “Cancel” key.

[0025] LCD panels 104 provide access to a test shell (discussed below)that provides system information and allows configuration of system 100.As discussed below, other methods of access to the test shell are alsoprovided by system 100. To avoid contention problems between the two LCDpanels 104, and the other methods of access to the test shell, a lockoutkey 406 is provided on LCD panels 104. A user can press lockout key 406to gain or release control of the test shell. In one embodiment, lockoutkey 406 includes an associated LED to light lockout key 406 and indicatea current lockout status.

[0026] In one embodiment, LCD panels 104 also provide additionalinformation to that displayed by LEDs 322 during start-up. If errors areencountered during the start-up sequence, LCD panels 104 provide moreinformation about the error without the operator having to attach aterminal to one of the SMC serial ports 310.

[0027] III. Server Management Card (SMC)

[0028] A. SMC Overview

[0029]FIG. 5 is an electrical block diagram illustrating majorcomponents of server management card (SMC) 300E. SMC 300E includes flashmemory 500, processor 502, dynamic random access memory (DRAM) 504, PCIbridge 506, field programmable gate array (FPGA) 508, output registers510A and 510B, input registers 512A and 512B, fan controllers 526A-526C(collectively referred to as fan controllers 526), network controller530, LAN switch 532, universal asynchronous receiver transmitter (UART)with modem 534, dual UART 536, UART with modem 538, clockgenerator/watchdog 540, battery 542, real time clock (RTC) 544,non-volatile random access memory (NVRAM) 546, I²C controllers 548A-548H(collectively referred to as I²C controllers 548), EEPROM 550, andtemperature sensor 324. In one embodiment, components of SMC 300E areconnected together via PCI buses 507. In one form of the invention, PCIbuses 507 are not routed between slots 110. Switched LAN signals throughLAN switch 532 are routed between slots 110.

[0030] Functions of SMC 300E include supervising the operation of othercomponents within system 100 (e.g. fan speed, temperature, card present)and reporting their health to a central location (e.g., externalmanagement network 320), reporting any failures to a central location(e.g., external management network 320), providing a LAN switch 532 toconnect console management LAN signals from the SMC 300E and hostprocessor cards 300A to an external management network 320, andproviding an initial boot configuration for the system 100.

[0031] B. SMC Processor And Memory

[0032] SMC 300E includes chassis management processor 502. In oneembodiment, chassis management processor 502, also referred to as SMCprocessor 502, is a StrongARM SA-110 processor with supporting buffer.In one embodiment, SMC 300E uses a Linux operating system. SMC 300E alsoruns server management application (SMA) software/firmware. In oneembodiment, the operating system and SMA are stored in flash memory 500.In one form of the invention, all information needed to power-up SMC300E, and for SMC 300E to become operational, are stored in flash memory500. In one embodiment, flash memory 500 includes 4 to 16 Mbytes ofstorage space to allow SMC 300E to boot-up as a stand-alone card (i.e.,no network connection needed).

[0033] SMC 300E also includes DRAM 504. In one embodiment, DRAM 504includes 32, 64 or 128 Mbytes of storage space. In one form of theinvention, a hardware fitted table is stored in DRAM 504. The hardwarefitted table includes information representing the physicalconfiguration of system 100. The hardware fitted table changes if thereis a physical change to system 100, such as by a hardware device beingadded to or removed from system 100. The hardware fitted table includeshardware type information (e.g., whether a device is anIA32/PA-RISC/Disk Carrier/RTM (i.e., rear transition module)/PSU/LCDpanel/Modem/Unknown device, etc.), hardware revision and serial number,status information, configuration information, and hot-swap statusinformation.

[0034] Processor 502 is coupled to FPGA 508. FPGA 508 includes 6 sets ofinput/output lines 522A-522F. Lines 522A are connected to jumpers forconfiguring SMC 300E. Lines 522B are hot swap lines for monitoring thehot swap status of cards 300. In one embodiment, hot swap lines 522Binclude 18 hot swap status input lines, which allow SMC 300E todetermine the hot swap status of the host processor cards 300A, harddisk cards 300B, managed Ethernet switch cards 300C and 300D, SMC reartransition modules 300F and 300G, and power supply units 114. Lines 522Care LED lines that are coupled to LEDs 322. Lines 522D are fan inputlines that are coupled to fan sensors 306 for monitoring the speed offans 304. Lines 522E are power supply status lines that are coupled topower supply units 114 for determining whether both, or only one powersupply unit 114 is present. Lines 522F are SMB alert lines forcommunicating alert signals related to SMB I²C buses 554B, 554D, and554F.

[0035] C. Clock, Battery & NVRAM

[0036] SMC 300E includes a real time clock (RTC) 544 and an associatedbattery 542 to preserve the clock. Real time clock 544 provides thecorrect time of day. SMC 300E also includes NVRAM 546 for storing clockinformation. In one embodiment, NVRAM 546 uses the same battery as realtime clock 544.

[0037] D. LAN switch

[0038] SMC 300E sends and receives management LAN communications throughPCI bridge 506 and controller 530 to LAN switch 532. In one embodiment,LAN switch 532 is an unmanaged LAN switch including 19 ports, with twoports connected to SMC rear transition modules 300F and 300G (shown inFIG. 3) via links 531A for communications with external managementnetwork 320 (shown in FIG. 3), 16 ports for connecting to the managementLAN connections of up to 16 host processor cards 300A via links 531Bthrough backplane 106, and one port for connecting to the SMC's LAN port(i.e., output of controller 530) via links 531C. SMC 300E providesmanagement support for console LAN management signals sent and receivedthrough LAN switch 532. SMC 300E provides control of management LANsignals of host processor cards 300A, managed Ethernet switches 300C and300D, SMC processor 502, and SMC rear transition modules 300F and 300G.SMC 300E monitors the status of the management LAN connections of up to16 host processor cards 300A to LAN switch 532, and reports an alarmevent if any of the connections are lost. FPGA 508 and LAN switch 532are coupled together via an RS-232 link 533 for the exchange of controland status information.

[0039] E. I²C Buses

[0040] Server system 100 includes eight I²C buses 554A-554H(collectively referred to as I²C buses 554) to allow communication withcomponents within system 100. I²C buses 554 are coupled to FPGA 508 viaI²C controllers 548. In one embodiment, the I²C buses 554 include 3intelligent platform management bus (IPMB) buses 554A, 554C, and 554E, 3system management bus (SMB) buses 554B, 554D, and 554F, a backplane IDbus (BP) 554G, and an I²C bus 554H for accessing SMC EEPROM 550 andchassis temperature sensor 324. A different number and configuration ofI²C buses 554 may be used depending upon the desired implementation. SMC300E maintains a system event log (SEL) within non-volatile flash memory500 for storing information gathered over I²C buses 554.

[0041] The IPMB I²C buses 554A, 554C, and 554E implement the intelligentplatform management interface (IPMI) specification. The IPMIspecification is a standard defining an abstracted interface to platformmanagement hardware. IPMI is layered over the standard I²C protocol. SMC300E uses one or more of the IPMB I²C buses 554A, 554C, and 554E toretrieve static data from each of the host processor cards 300A and harddisk cards 300B. The static data includes identification information foridentifying each of the cards 300A and 300B. Each slot 110 in system 100can be individually addressed to retrieve the static configuration datafor the card 300 in that slot 110. In one embodiment, the host processorcards 300A and hard disk cards 300B each include an EEPROM 302A (shownin FIG. 3) that stores the static identification information retrievedover IPMB I²C buses 554A, 554C, and 554E. In one embodiment, each EEPROM302A contains the type of card, the name of the card, the hardwarerevision of the card, the card's serial number and card manufacturinginformation.

[0042] SMC 300E also uses one or more of the IPMB I²C buses 554A, 554C,and 554E, to retrieve dynamic environmental information from each of thehost processor cards 300A and hard disk cards 300B. In one embodiment,this dynamic information is held in a second EEPROM 302B (shown in FIG.3) on each of the cards 300A and 300B. In one form of the invention, thedynamic board data includes card temperature and voltage measurements.In one embodiment, SMC 300E can write information to the EEPROMs 302Aand 302B on cards 300.

[0043] The three SMB I²C buses 554B, 554D, and 554F also implement theIPMI specification. The three SMB I²C buses 554B, 554D, and 554F, arecoupled to LEDs 322, the two LCD panels 104, the dual redundant powersupply units 114, and some of the host processor cards 300A. SMC 300Euses one or more of the SMB I²C buses 554B, 554D, and 554F, to provideconsole communications via the LCD panels 104. In order for the keypadkey-presses on the LCD panels 104 to be communicated back to SMC 300E,an alert signal is provided when keys are pressed that causes SMC 300Eto query LCD panels 104 for the keys that were pressed.

[0044] SMC 300E communicates with power supply units 114 via one or moreof the SMB I²C buses 554B, 554D, and 554F to obtain configuration andstatus information including the operational state of the power supplyunits 114. In one embodiment, the dual redundant power supply units 114provide voltage rail measurements to SMC 300E. A minimum and maximumvoltage value is stored by the power supply units 114 for each measuredrail. The voltage values are polled by SMC 300E at a time intervaldefined by the current configuration information for SMC 300E. If avoltage measurement goes out of specification, defined by maximum andminimum voltage configuration parameters, SMC 300E generates an alarmevent. In one embodiment, power supply units 114 store configuration andstatus information in their associated EEPROMs 323 (shown in FIG. 3).

[0045] Backplane ID Bus (BP) 554G is coupled to backplane EEPROM 314(shown in FIG. 3) on backplane 106. SMC 300E communicates with thebackplane EEPROM 314 over the BP bus 554G to obtain backplanemanufacturing data, including hardware identification and revisionnumber. On start-up, SMC 300E communicates with EEPROM 314 to obtain themanufacturing data, which is then added to the hardware fitted table.The manufacturing data allows SMC 300E to determine if it is in thecorrect chassis for the configuration it has on board, since it ispossible that the SMC 300E has been taken from a different chassis andeither hot-swapped into a new chassis, or added to a new chassis and thechassis is then powered up. If there is no valid configuration on board,or SMC 300E cannot determine which chassis it is in, then SMC 300E waitsfor a pushed configuration from external management network 320, or fora manual user configuration via one of the connection methods discussedbelow.

[0046] In one embodiment, there is a single temperature sensor 324within system 100. SMC 300E receives temperature information fromtemperature sensor 324 over I²C bus 554H. SMC 300E monitors and recordsthis temperature and adjusts the speed of the cooling fans 304accordingly, as described below. SMC also uses I²C bus 554H to accessEEPROM 550, which stores board revision and manufacture data for SMC300E.

[0047] F. Serial Ports

[0048] SMC 300E includes 4 RS-232 interfaces 310A-310D (collectivelyreferred to as serial ports 310). RS-232 serial interface 310A is via a9-pin Male D-type connector on the front panel of SMC 300E. The otherthree serial ports 3100B-310D are routed through backplane 106. Thefront panel RS-232 serial interface 310A is connected via a UART with afull modem 534 to FPGA 508, to allow monitor and debug information to bemade available via the front panel of SMC 300E. Backplane serial port310D is also connected via a UART with a full modem 538 to FPGA 508. Inone embodiment, backplane serial port 310D is intended as a debug orconsole port. The other two backplane serial interfaces 310B and 310Care connected via a dual UART 536 to FPGA 508, and are routed to managedEthernet switches 300C and 300D through backplane 106. These twobackplane serial interfaces 310B and 310C are used to connect to andconfigure the managed Ethernet switch cards 300C and 300D, and to obtainstatus information from the managed Ethernet switch cards 300C and 300D.

[0049] G. Fans And Temperature Control

[0050] In one embodiment, server system 100 includes six chassis fans304. Server system 100 includes temperature sensor 324 to monitor thechassis temperature, and fan sensors 306 to monitor the six fans 304. Inone embodiment, fan sensors 306 indicate whether a fan 304 is rotatingand the fan's speed setting. In one form of the invention, FPGA 508includes 6 fan input lines 522D (i.e., one fan input line 522D from eachfan sensor 306) to monitor the rotation of the six fans 304, and asingle fan output line 524 coupled to fan controllers 526A-526C. Fancontrollers 526A-526C control the speed of fans 304 by a PWM (pulsewidth modulation) signal via output lines 528A-528F. If a fan 304stalls, the monitor line 522D of that fan 304 indicates this conditionto FPGA 508, and an alarm event is generated. The speed of fans 304 isvaried to maintain an optimum operating temperature versus fan noisewithin system 100. If the chassis temperature sensed by temperaturesensor 324 reaches or exceeds a temperature alarm threshold, an alarmevent is generated. When the temperature reduces below the alarmthreshold, the alarm event is cleared. If the temperature reaches orexceeds a temperature critical threshold, the physical integrity of thecomponents within system 100 are considered to be at risk, and SMC 300Eperforms a system shut-down, and all cards 300 are powered down exceptSMC 300E. When the chassis temperature falls below the criticalthreshold and has reached the alarm threshold, SMC 300E restores thepower to all of the cards 300 that were powered down when the criticalthreshold was reached.

[0051] In one embodiment, SMC 300E controls the power state of cards 300using power reset (PRST) lines 514 and power off (PWR_OFF) lines 516.FPGA 508 is coupled to power reset lines 514 and power off lines 516 viaoutput registers 510A and 510B, respectively. In one embodiment, powerreset lines 514 and power off lines 516 each include 19 output linesthat are coupled to cards 300. SMC 300E uses power off lines 516 to turnoff the power to selected cards 300, and uses power reset lines 514 toreset selected cards 300. In one embodiment, a lesser number of powerreset and power off lines are used for the 10 slot chassisconfiguration.

[0052] H. Clock Generator/Watchdog

[0053] SMC 300E is protected by both software and hardware watchdogtimers. The watchdog timers are part of clock generator/watchdog block540, which also provides a clock signal for SMC 300E. The hardwarewatchdog timer is started before software loading commences to protectagainst failure. In one embodiment, the time interval is set long enoughto allow a worst-case load to complete. If the hardware watchdog timerexpires, SMC processor 502 is reset.

[0054] I. Modes Of Operation

[0055] In one embodiment, SMC 300E has three phases or modes ofoperation—Start-up, normal operation, and hot swap. The start-up mode isentered on power-up or reset, and controls the sequence needed to makeSMC 300E operational. SMC 300E also provides minimal configurationinformation to allow chassis components to communicate on the managementLAN. The progress of the start-up procedure can be followed on LEDs 322,which also indicate any errors during start-up.

[0056] The normal operation mode is entered after the start-up mode hascompleted. In the normal operation mode, SMC 300E monitors the health ofsystem 100 and its components, and reports alarm events. SMC 300Emonitors the chassis environment, including temperature, fans, inputsignals, and the operational state of the host processor cards 300A.

[0057] SMC 300E reports alarm events to a central point, namely an alarmevent manager, via the management LAN (i.e., through LAN switch 532 andone of the two SMC rear transition modules 300F or 300G to externalmanagement network 320). The alarm event manager is an external modulethat is part of external management network 320, and that handles thealarm events generated by server system 100. The alarm event managerdecides what to do with received alarms and events, and initiates anyrecovery or reconfiguration that may be needed. In addition to sendingthe alarm events across the management network, a system event log (SEL)is maintained in SMC 300E to keep a record of the alarms and events. TheSEL is held in non-volatile flash memory 500 in SMC 300E and ismaintained over power cycles, and resets of SMC 300E.

[0058] In the normal operation mode, SMC 300E may receive and initiateconfiguration commands and take action on received commands. Theconfiguration commands allow the firmware of SMC processor 502 and thehardware controlled by processor 502 to be configured. This allows theoperation of SMC 300E to be customized to the current environment.Configuration commands may originate from the management network 320,one of the local serial ports 310 via a test shell (discussed below), orone of the LCD panels 104.

[0059] The hot swap mode is entered when there is an attempt to remove acard 300 from system 100. In one embodiment, all of the chassis cards300 can be hot swapped, including SMC 300E, and the two power supplyunits 114. An application shutdown sequence is initiated if a card 300is to be removed. The shutdown sequence performs all of the steps neededto ready the card 300 for removal.

[0060] In one embodiment, FPGA 508 includes 18 hot swap status inputs522B. These inputs 522B allow SMC 300E to determine the hot swap statusof host processor cards 300A, hard disk cards 300B, managed Ethernetswitch cards 300C and 300D, SMC rear transition module cards 300F and300G, and power supply units 114. The hot-swap status of the SMC card300E itself is also determined through this interface 522B.

[0061] An interrupt is generated and passed to SMC processor 502 if anyof the cards 300 in system 100 are being removed or installed. SMC 300Emonitors board select (BD_SEL) lines 518 and board healthy (HEALTHY)lines 520 of cards 300 in system 100. In one embodiment, board selectlines 518 and healthy lines 520 each include 19 input lines, which areconnected to FPGA 508 via input registers 512A and 512B, respectively.SMC 300E monitors the board select lines 518 to sense when a card 300 isinstalled. SMC 300E monitors the healthy lines 520 to determine whethercards 300 are healthy and capable of being brought out of a reset state.

[0062] When SMC 300E detects that a card has been inserted or removed,an alarm event is generated. When a new card 300 is inserted in system100, SMC 300E determines the type of card 300 that was inserted bypolling the identification EEPROM 302A of the card 300. Information isretrieved from the EEPROM 302A and added to the hardware fitted table.SMC 300E also configures the new card 300 if it has not been configured,or if its configuration differs from the expected configuration. When acard 300, other than the SMC 300E, is hot-swapped out of system 100, SMC300E updates the hardware fitted table accordingly.

[0063] In one embodiment, SMC 300E is extracted in three stages: (1) aninterrupt is generated and passed to the SMC processor 502 when theextraction lever 308 on the SMC front panel is set to the “extraction”position in accordance with the Compact PCI specification, indicatingthat SMC 300E is about to be removed; (2) SMC processor 502 warns theexternal management network 320 of the SMC 300E removal and makes theextraction safe; and (3) SMC processor 502 indicates that SMC may beremoved via the blue hot swap LED 322. SMC 300E ensures that anyapplication download and flashing operations are complete before the hotswap LED 322 indicates that the card 300E may be removed.

[0064] J. User Connectivity

[0065] In one embodiment, there are two test shells implemented withinSMC 300E. There is an application level test shell that is a normal,run-time, test shell accessed and used by users and applications. Thereis also a stand-alone test shell that is a manufacturer test shellresiding in flash memory 500 that provides manufacturing leveldiagnostics and functions. The stand-alone test shell is activated whenSMC 300E boots and an appropriate jumper is in place on SMC 300E. Thestand-alone test shell allows access to commands that the user wouldnot, or should not have access to.

[0066] The test shells provide an operator interface to SMC 300E. Thisallows an operator to query the status of system 100 and (with therequired authority level) to change the configuration of system 100.

[0067] A user can interact with the test shells by a number of differentmethods, including locally via a terminal directly attached to one ofthe serial ports 310, locally via a terminal attached by a modem to oneof the serial ports 310, locally via one of the two LCD panels 104, andremotely via a telnet session established through the management LAN320. A user may connect to the test shells by connecting a terminal toeither the front panel serial port 31 OA or rear panel serial ports310B-310D of SMC 300E, depending on the console/modem serial portconfiguration. The RS-232 and LAN connections provide a telnet consoleinterface. LCD panels 104 provide the same command features as thetelnet console interface. SMC 300E can function as either a dial-infacility, where a user may establish a link by calling to the modem, oras a dial-out facility, where SMC 300E can dial out to a configurednumber.

[0068] The test shells provide direct access to alarm and event statusinformation. In addition, the test shells provides the user with accessto other information, including temperature logs, voltage logs, chassiscard fitted table, and the current setting of all the configurationparameters. The configuration of SMC 300E may be changed via the testshells. Any change in configuration is communicated to the relevantcards 300 in system 100. In one embodiment, configuration informationdownloaded via a test shell includes a list of the cards 300 expected tobe present in system 100, and configuration data for these cards 300.The configuration information is stored in flash memory 500, and is usedevery time SMC 300E is powered up.

[0069] K. Console LAN Configuration

[0070] In one embodiment, SMC 300E uses the I²C buses 554 coupled tohost processor cards 300A to set the internet protocol (IP) addressinformation. As mentioned above, the I²C buses 554 coupled to hostprocessor cards 300A use the intelligent platform management interface(IPMI). IPMI provides the definition to the structure of basic I²Cmaster read and write commands. In one form of the invention, SMC 300Eaugments the IPMI protocol with additional host processor cardconfiguration commands that send over the IPMI I²C buses 554 the IPinformation required to get a console or management LAN up and running.In one embodiment, the configuration parameters downloaded from SMC 300Eto host processor cards 300A over IPMI I²C buses 554 include: IPaddress, gateway address, subnet address, and host name. A hostprocessor card 300A that needs the use of a console LAN, will alwayshave its IPMI interface active, despite the boot state of the hostprocessor card 300A, including powered off. With the possibility that acustomer could move a working host processor card 300A to a differentchassis and possibly a different LAN, what was previously a unique LANaddress could later conflict with an existing LAN address. So theability to set LAN address information in an inoperable state of a hostprocessor card 300A is important.

[0071] By using the already existing IPMI I²C buses 554 to set the IPaddress information, there is virtually no added cost to configuresystem 100, and system 100 is robust. In contrast to the prior arttechnique of providing an RS-232 connection to each individual server toset IP address information, the use of an IPMI I²C bus 554 allows formultiple devices on one bus, thus greatly reducing the complexity of thesystem. This also allows for better remote management, since it isundesirable to have multiple connections into a server, or having tophysically be present at the server to change configurations. A user maylog in remotely to management card 300E through management LAN 320,provide the IP address information to management card 300E, which thensends the IP address information to host processor cards 300A using theIPMI I²C buses 554.

[0072] Although specific embodiments have been illustrated and describedherein for purposes of description of the preferred embodiment, it willbe appreciated by those of ordinary skill in the art that a wide varietyof alternate and/or equivalent implementations may be substituted forthe specific embodiments shown and described without departing from thescope of the present invention. Those with skill in the chemical,mechanical, electro-mechanical, electrical, and computer arts willreadily appreciate that the present invention may be implemented in avery wide variety of embodiments. This application is intended to coverany adaptations or variations of the preferred embodiments discussedherein. Therefore, it is manifestly intended that this invention belimited only by the claims and the equivalents thereof.

What is claimed is:
 1. A server system comprising: a plurality of hostprocessor cards; a management card coupled to the plurality of hostprocessor cards via at least one bus, the management card including atleast one user interface for receiving network address information froma user, the management card configured to send received network addressinformation to the plurality of host processor cards via the at leastone bus, thereby configuring the host processor cards for management LANcommunications.
 2. The server system of claim 1, wherein the at leastone bus is an I²C bus.
 3. The server system of claim 2, wherein the atleast one bus is an intelligent platform management interface (IPMI) I²Cbus.
 4. The server system of claim 3, wherein the network addressinformation sent from the management card to the plurality of hostprocessor cards is sent using an augmented IPMI protocol that includesadditional host processor card configuration commands.
 5. The serversystem of claim 1, wherein the network address information includesinternet protocol (IP) address information.
 6. The server system ofclaim 5, wherein the IP address information includes an IP address,gateway address, subnet address, and host name.
 7. The server system ofclaim 1, wherein the at least one user interface includes at least oneserial port and at least one LAN interface.
 8. The server system ofclaim 7, wherein the at least one user interface further includes atleast one LCD panel mounted on the server system.
 9. A server managementcard for a server system having a plurality of host processor cards, theserver management card comprising: at least one user interface forallowing a user to enter network address information; at least one I²Cbus connection for connecting the server management card to theplurality of host processor cards via at least one I²C bus; and acontroller configured to output entered network address information tothe plurality of host processor cards via the at least one I²C busconnection, thereby configuring the plurality of host processor cardsfor network communications.
 10. The server management card of claim 9,wherein the at least one I²C bus is an intelligent platform managementinterface (IPMI) I²C bus.
 11. The server management card of claim 10,wherein the network address information output from the servermanagement card to the plurality of host processor cards is sent usingan augmented IPMI protocol that includes additional host processor cardconfiguration commands.
 12. The server management card of claim 9,wherein the network address information includes internet protocol (IP)address information.
 13. The server management card of claim 12, whereinthe IP address information includes an IP address, gateway address,subnet address, and host name.
 14. The server management card of claim9, wherein the at least one user interface includes at least one serialport, at least one LAN interface, and at least one LCD panel mounted onthe server system.
 15. A method of configuring host processor cards in aserver system for management network communications, the methodcomprising: providing a management card in the server system having atleast one user interface; providing at least one bus connecting themanagement card and the host processor cards; entering network addressinformation to the management card through the at least one userinterface; and sending entered network address information from themanagement card to the host processor cards, thereby configuring thehost processor cards for management network communications.
 16. Themethod of claim 15, wherein the at least one bus is an I²C bus.
 17. Themethod of claim 16, wherein the at least one bus is an intelligentplatform management interface (IPMI) I²C bus.
 18. The method of claim17, wherein the network address information sent from the managementcard to the host processor cards is sent using an augmented IPMIprotocol that includes additional host processor card configurationcommands.
 19. The method of claim 15, wherein the network addressinformation includes an internet protocol (IP) address, gateway address,subnet address, and host name.
 20. The method of claim 15, wherein theat least one user interface includes at least two of a serial port, aLAN interface, and an LCD panel mounted on the server system.